Skip to content

Release 0.7.0 - #28

Closed
schreck61 wants to merge 1 commit into
mainfrom
release-0.7.0
Closed

schreck61 wants to merge 1 commit into
mainfrom
release-0.7.0

Conversation

@schreck61

Copy link
Copy Markdown
Owner

What

Sets the version to 0.7.0 for the next release.

  • Version: Cargo.toml and Cargo.lock, and THIRD_PARTY_LICENSES.md, regenerated with packaging/licenses.sh because it lists the app's own version.
  • Places that name the current version: the opening of docs/architecture.md, the bug-report template's placeholder, the release examples in packaging/README.md, and ACCESSIBILITY.md's Last reviewed line, which named this release as "the release after 0.6.0".
  • About window picture: it shows the version, so it is retaken with this branch's build (TS_ABOUT=1, as Appendix A of docs/architecture.md lists it) and cut at the same place. Only the version's digit differs from the earlier picture. Its alt text and §9.4's note on where the pictures come from say 0.7.0.
  • Unchanged: ROADMAP.md's Last reviewed line keeps "after version 0.6.0", since the roadmap wasn't reviewed again. Mentions of what earlier versions did stay as they are.

Why 0.7.0

Since 0.6.0, main has gained failures at the cooperative crossing (#25), overlap counts in bench's strategy tables (#24), a fix that keeps train from writing outside its weights folder (#27), and async-executor 1.14.1 (#26). Every package released so far was built with async-executor 1.14.0, which was yanked for a use-after-free. So far only the browser version, which is rebuilt from main, has these changes.

The library's public API also changed incompatibly:

  • Reason has the new variants Emergency, Stranded and Disabled.
  • Vehicle has the new fields disabled and the crate-private blind_until, so other crates can no longer build one with a struct literal.
  • Plan, CoopStats and CoopManager have new public fields, and PlanKind is a new public enum.

GOVERNANCE.md commits to Semantic Versioning, so this release is 0.7.0 rather than 0.6.1. Nothing changes for weights files: the code that reads and writes them is the same as in 0.6.0.

After merging

Tag the merged commit v0.7.0 and push the tag, as in packaging/README.md's Making a release. The release workflow builds and signs every package into a draft release, which is reviewed and then published. Publishing also sends the crate to crates.io.

Testing

On Rust 1.100.0, the version CI uses:

  • cargo fmt --all --check, and for fuzz/
  • cargo clippy --locked --release --all-targets -- -D warnings, and its wasm32 counterpart
  • cargo test --locked --release
  • packaging/licenses.sh --check
  • cargo deny --locked check

Set the version to 0.7.0 in Cargo.toml and Cargo.lock, and regenerate
the attributions, which list the app's own version. Update the places
that name the current version: the opening of docs/architecture.md,
the bug-report template's placeholder, the release examples in
packaging/README.md, and the Last reviewed line of ACCESSIBILITY.md,
which named this release as the one after 0.6.0.

The About window picture in section 9.4 of docs/architecture.md shows
the version, so it is retaken with this build, cut at the same place:
only the version's digit differs from the earlier picture. Its alt text
and the section's note on where its pictures come from say 0.7.0.

This is 0.7.0 rather than 0.6.1 because the library's public API
changed incompatibly since 0.6.0: Reason has new variants, Vehicle has
new fields, one of them crate-private, and Plan, CoopStats and
CoopManager have new public fields.

Signed-off-by: Jim Schreckengast <schreck@gmail.com>
@schreck61
schreck61 enabled auto-merge (rebase) November 16, 2026 06:47
@schreck61
schreck61 disabled auto-merge November 16, 2026 06:51
@schreck61 schreck61 mentioned this pull request Nov 16, 2026
@schreck61

Copy link
Copy Markdown
Owner Author

Replaced by #29, which has the same files and a commit message that counts only the API changes that are incompatible (Reason's new variants and the new fields of Plan and CoopStats).

@schreck61 schreck61 closed this Nov 16, 2026
@schreck61
schreck61 deleted the release-0.7.0 branch November 16, 2026 07:36
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant